8371 Interface Configuration
This chapter describes how to use the 10/100-Mbps Ethernet
interface. It includes the following section:
You can use the interface command from the GWCON environment to
display the following statistics.
+interface
Self-Test Self-Test Maintenance
Net Net' Interface Slot-Port Passed Failed Failed
0 0 Eth/0 Slot: 0 Port: 1 0 0 0
1 1 Eth/1 Slot: 0 Port: 2 0 0 0
2 2 Eth/2 Slot: 0 Port: 3 0 0 0
3 3 Eth/3 Slot: 0 Port: 4 0 0 0
4 4 Eth/4 Slot: 0 Port: 5 0 0 0
5 5 Eth/5 Slot: 0 Port: 6 0 0 0
6 6 Eth/6 Slot: 0 Port: 7 0 0 0
7 7 Eth/7 Slot: 0 Port: 8 0 0 0
8 8 Eth/8 Slot: 0 Port: 9 0 0 0
9 9 Eth/9 Slot: 0 Port: 10 0 0 0
10 10 Eth/10 Slot: 0 Port: 11 0 0 0
11 11 Eth/11 Slot: 0 Port: 12 0 0 0
12 12 Eth/12 Slot: 0 Port: 13 0 0 0
13 13 Eth/13 Slot: 0 Port: 14 0 0 0
14 14 Eth/14 Slot: 0 Port: 15 0 0 0
15 15 Eth/15 Slot: 0 Port: 16 0 0 0
16 16 Eth/16 Slot: 1 Port: 1 0 0 0
17 17 Eth/17 Slot: 1 Port: 2 0 0 0
18 18 Eth/18 Slot: 1 Port: 3 0 0 0
19 19 Eth/19 Slot: 1 Port: 4 0 0 0
20 20 Eth/20 Slot: 1 Port: 5 0 0 0
21 21 Eth/21 Slot: 1 Port: 6 0 0 0
22 22 Eth/22 Slot: 1 Port: 7 0 0 0
23 23 Eth/23 Slot: 1 Port: 8 0 0 0
24 24 Eth/24 Slot: 2 Port: 1 0 0 0
25 25 Eth/25 Slot: 2 Port: 2 0 0 0
26 26 Eth/26 Slot: 2 Port: 3 0 0 0
27 27 Eth/27 Slot: 2 Port: 4 0 0 0
28 28 Eth/28 Slot: 2 Port: 5 0 0 0
29 29 Eth/29 Slot: 2 Port: 6 0 0 0
30 30 Eth/30 Slot: 2 Port: 7 0 0 0
31 31 Eth/31 Slot: 2 Port: 8 0 0 0
32 32 Eth/32 Slot: 3 Port: 1 0 0 0
33 33 Eth/33 Slot: 3 Port: 2 0 0 0
34 34 Eth/34 Slot: 3 Port: 3 0 0 0
35 35 Eth/35 Slot: 3 Port: 4 0 0 0
36 36 ATM/0 Slot: 1 Port: 4 0 1 0
37 37 ATM/1 Slot: 1 Port: 2 0 1 0
38 38 ATM/2 Slot: 2 Port: 1 0 1 0
39 39 ATM/3 Slot: 2 Port: 2 0 1 0
40 40 Eth/36 0 0 0
41 41 Eth/37 0 0 0
42 42 Eth/38 0 0 0
43 43 Eth/39 0 0 0
44 44 Eth/40 0 0 0
45 55 Eth/42 0 0 0
46 56 Eth/43 0 0 0
47 57 Eth/44 0 0 0
48 58 Eth/45 0 0 0
49 59 Eth/46 0 0 0
50 50 Eth/47 0 0 0
51 51 Eth/48 0 0 0
52 52 Eth/49 0 0 0
53 53 Eth/50 0 0 0
54 54 Eth/51 0 0 0
55 65 Eth/52 0 0 0
56 66 Eth/53 0 0 0
57 67 Eth/54 0 0 0
58 68 Eth/55 0 0 0
59 69 Eth/56 0 0 0
60 60 Eth/57 0 0 0
61 61 Eth/58 0 0 0
62 62 Eth/59 0 0 0
63 63 Eth/60 0 0 0
+
These statistics have the following meaning:
- Nt
- Global network number.
- Nt'
- This field is for the serial interface card. Disregard the
output.
- Interface
- Interface name and its instance number.
- Self-Test: Passed
- Number of self-tests that succeeded.
- Self-Test: Failed
- Number of self-tests that failed.
- Maintenance: Failed
- Number of maintenance failures.
- Physical address
- The Ethernet address of the device currently in use. This may be
the PROM address or an address overwritten by some other protocol.
- PROM address
- The permanent unique Ethernet address in the PROM for this Ethernet
interface.
- Actual address
-
- Configured duplex
- The value configured for duplex. Values can be Half Duplex, Full
Duplex, or Auto-Negotiation.
- Actual duplex
- The value at which the adapter is presently operating. It might be
different from the value configured, depending on the switch
capability. If the adapter is not Up, the value displayed will be
Unknown. Otherwise the value can be Half Duplex or Full
Duplex.
Whenever the link partner (switch or hub) does not participate during the
negotiation phase, *** will follow the actual duplex mode value. When
*** is indicated the operational duplex value should be verified on the switch
or hub for consistency.
Most hubs (unlike switches) can only support half-duplex mode, and are not
capable of negotiation. As such the *** indication will usually be
displayed when the interface is connected to a hub.
A message will also be logged via the ELS system whenever a possibility of
a mis-match in duplex mode exists.
Note: | If the link partner (switch or hub) to which the interface is connected does
not respond during the negotiation phase, the two may result in operating in
different duplex modes. That is, the interface may be operating in
half-duplex, while the switch port is operating in full duplex mode. A
mismatch in the duplex mode can result in severe performance
degradation. See "10/100-Mbps Ethernet Configuration Commands" for important information regards speed and duplex
configurations.
|
- Configured speed
- The value configured for speed. Values can be 10 Mbps, 100Mbps, or
Auto-Negotiation.
- Actual speed
- The speed at which the adapter is presently operating.If the
adapter is not Up, the value displayed will be Unknown.
Otherwise the value can be 10 Mbps or 100 Mbps.
- Input statistics:
-
- failed, packet too long or failed, frame too long
- The Failed, Packet Too Long counter increments when the interface receives
a packet that is larger than the maximum size of 1518 bytes for an Ethernet
frame. This data is exported via SNMP as the dot3StatsFrameTooLongs
counter.
- failed, CRC error or failed, FCS (Frame Check Sequence) error
- The Failed, CRC (Cyclic Redundancy Check) Error counter increments when
the interface receives a packet with a CRC error. This data is exported
via SNMP as the dd3StatsFCSErrors counter.
- failed, alignment error
- The Failed, Framing Error counter increments when the interface receives a
packet where the length in bits is not a multiple of eight.
- failed, receive overflow
- Overflow error indicates that the receiver has lost all or part of the
incoming frame, due to an inability to move data from the receive FIFO into
memory buffer before the internal FIFO overflowed.
- receive underrun
- Indicates the number of times the adapter did not have a second buffer to
store a long frame (requiring more than one buffer).
- Output statistics:
-
- one retry
- Indicates that exactly one retry was needed to transmit a frame.
This data is exported via SNMP as the dot3StatsDeferredTransmissions
counter.
- single collision
- The Single Collision counter increments when a packet has a collision on
the first transmission attempt, and then successfully sends the packet on the
second transmission attempt. This data is exported via SNMP as the
dot3StatsSingleCollisionFrames counter.
- multiple collisions
- The Multiple Collisions counter increments when a packet has multiple
collisions before being successfully transmitted. This data is exported
via SNMP as the dot3MultipleCollisionFrames counter.
- failed, transmit underflow
- Transmit underrun indicates that transmitter has truncated a message
because it could not read data from the memory fast enough. It also
indicates that the FIFO on the adapter has emptied out before the end of the
frame was reached. IFO into memory buffer before the internal FIFO
overflowed.
- failed, excess collisions
- The Failed, Excess Collisions counter increments when a packet
transmission fails due to 16 successive collisions. This error
indicates a high volume of network traffic or hardware problems with the
network. This data is exported via SNMP as the
dot3StatsExcessiveCollisions counter.
- memory error
- Memory errors occur when the adapter is not given access to the system
interface bus within the programmable length of time. This error will
normally occur during transmit operations, indicating transmit
underrun.
Specifying values other than auto for speed or duplex on the
10/100 Ethernet interface or its link partner (switch port) can result in
duplex mode mismatch or link activation failures.
Link activation failures due to configuration mismatches will occur on the
IBM 8371 whenever the speed configured at both ends are not identical.
When either speed or duplex value is auto-negotiate, both speed
and duplex will be negotiated with the link partner and its configured speed
or duplex will be used.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]